home *** CD-ROM | disk | FTP | other *** search
- Path: inforamp.net!ts4-03
- From: rmorin@inforamp.net (Randy Charles Morin)
- Newsgroups: comp.lang.c++
- Subject: Re: Coding Standards
- Date: Tue, 26 Mar 96 07:48:41 GMT
- Organization: MiddleWorld SoftWare
- Message-ID: <4j87hg$q74@sam.inforamp.net>
- References: <4hj8ek$elu@sam.inforamp.net> <4hktar$5o2@galaxy.ucr.edu> <4hmqol$97j@abacus.abasoft.co.uk> <4hsg8r$pmm@sam.inforamp.net> <4i9o6j$p4l@daisy.pgh.wec.com> <4idskb$pc1@sam.inforamp.net> <314EBD08.43BC@virtus.com> <4io2i7$n9v@sam.inforamp.net> <4isu2t$opo@jan <4j2jot$svj@sam.inforamp.net> <4j4gkq$j6c@janus.pec.co.nz>
- NNTP-Posting-Host: ts4-03.tor.inforamp.net
- X-Newsreader: News Xpress Version 1.0 Beta #4
-
- In article <4j4gkq$j6c@janus.pec.co.nz>,
- JohnM@hypatia.pec.co.nz (John Marshall) wrote:
- >Huh? My post-compilation objects are monolithic applications, and if my
- >data types change, they don't know about it until I make the effort to
- >type "make" to make a new version.
-
- When you think of your post-compilation objects as being applications,
- you have completely ignored the object oriented ideology. Think about
- sharing objects and I think you will understand.
-
- >Oh, so I'm writing a *library*. And it's shipped to users separately from
- >the applications that use it. Why didn't you say so?
-
- I did not say a library. But that is another example. We are talking
- about a coding standard for a large corporation. Their coding standard
- should be able to handle every situation they are presented with.
-
- >> If you don't have
- >> inline accessors, then you don't have a problem. Is this so hard to
- >> understand?
- >Well, yes, as usual it is hard to understand, simply because it's not true.
- >Inline accessors are only one of the things you have to worry about.
-
- Obviously. So what you are saying is that we shouldn't attempt to
- hide data, because it is only one of many things we need to do to
- properly hide data. Why not implement all of these THINGS? And to
- accomplish this object oriented goal, you need to use all of these
- THINGS. Including proper data hiding.
-
- >For example, depending on your DLL technology, you may have to be very
- >careful about rearranging or adding to the list of externally visible
- >functions, for fear of changing entry point offsets.
-
- So what you are saying is that if you use ordinal numbering of functions,
- then you don't have a problem and you can rearrange and add functions
- without fear of changing entry points.
-
- >On the other hand, if one *is* writing a monolithic application, then inline
- >accessors are no more harmful than anything else.
-
- Agreed. Inline accessors are a great asset that can be used to
- enhance the performance of some applications. I never said that you
- should outlaw the use of inline accessors. I was arging that
- arbitrarily mandating that all accessors be inline is wrong. You
- disagreed. I assume that your entire argument was based on this
- misunderstanding.
-
- >It seems to me that what developers need is knowledge of all these
- >implications, rather than just blind adherence to some incomplete rule
- >like "NEVER use the word inline".
-
- Agree. Again, you are confirming my exact sentiments.
-
-
-
- Agrivar
-
- aka Randy Charles Morin
- MiddleWorld SoftWare
- Canada: 1-800-363-3780
- Other: 905-279-2087
-